Skip to content

OSDOCS Document how to perform boot image updates on bare metal clusters#109158

Open
mburke5678 wants to merge 5 commits intoopenshift:mainfrom
mburke5678:mco-manual-boot-image-baremetal
Open

OSDOCS Document how to perform boot image updates on bare metal clusters#109158
mburke5678 wants to merge 5 commits intoopenshift:mainfrom
mburke5678:mco-manual-boot-image-baremetal

Conversation

@mburke5678
Copy link
Copy Markdown
Contributor

@mburke5678 mburke5678 commented Mar 27, 2026

https://redhat.atlassian.net/browse/OSDOCS-18560

Link to docs preview:
Manually updating the boot image on a bare-metal cluster -- New module. Final location TBD.

QE review:

  • QE has approved this change.

@mburke5678 mburke5678 added this to the Planned for 4.22 GA milestone Mar 27, 2026
@openshift-ci openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 27, 2026
@ocpdocs-previewbot
Copy link
Copy Markdown

ocpdocs-previewbot commented Mar 27, 2026

= Manually updating the boot image on a bare-metal cluster

[role="_abstract"]
For a bare-metal cluster, you can manually update the boot image for your cluster by configuring your machine sets to use the latest {product-title} image as the boot image to help ensure any new nodes can scale up properly.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not strictly true, we are migrating the cluster to use the new method of scaling new nodes into the cluster. The user by themselves are not updating the bootimage, like our other help docs. This is more of a one time action, and we should make that clear.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Too much copying/pasting!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is this?
"For a bare-metal cluster that was installed with {product-title} version 4.9 or earlier, you need to change how the cluster provisions new nodes in order to update the boot image used with those nodes."

Comment thread modules/mco-update-boot-images-ibm-bare-metal.adoc Outdated
Comment thread modules/mco-update-boot-images-ibm-bare-metal.adoc Outdated
Comment thread modules/mco-update-boot-images-ibm-bare-metal.adoc Outdated
Comment thread modules/mco-update-boot-images-ibm-bare-metal.adoc Outdated
Comment thread modules/mco-update-boot-images-ibm-bare-metal.adoc Outdated

.Verification

. Scale up a machine set to check that the new node is using the new boot image:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that this procedure is slightly different - a new BareMetalHost needs to be available as well, see https://gist.github.com/djoshy/93209abaec7f8474a1bdbc47551fc626#verifying-new-boot-image-optional

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added that as a prerequisite.

@djoshy
Copy link
Copy Markdown

djoshy commented Mar 30, 2026

same as #109084 (comment)

/retitle OSDOCS Document how to perform boot image updates on bare metal clusters

@openshift-ci openshift-ci Bot changed the title OSDOCS Document how to perform boot image updates on marketplace clusters bare metal OSDOCS Document how to perform boot image updates on bare metal clusters Mar 30, 2026
@mburke5678
Copy link
Copy Markdown
Contributor Author

@ptalgulk01 @sergiordlr PTAL

@mburke5678 mburke5678 force-pushed the mco-manual-boot-image-baremetal branch from 107a334 to 866fd66 Compare March 31, 2026 20:48
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 31, 2026

@mburke5678: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.22 size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants